publishSchedule

Causes the server to export a schedule. The actual schedule data is not returned in the reply message.

Sample Request

mmRequest command="publishSchedule" station="ID" [version="1"] [client=""] [userData=""]>
	<contents>
		<startTime>yyyy-mm-ddThh:00:00</startTime>
		<endTime> yyyy-mm-ddThh:00:00</endTime>
		[<design>design name</design>]
		[<fileSpec>full path and file</fileSpec>]
	</contents>
</mmRequest>

Request Notes

startTime – The first hour to include in the reply. This is the first full hour that will be included.

 

endTime – The last hour to include in the reply. This is the last full hour that will be included.

 

Note that currently requests for more than 24 hours of schedule data will not be accepted. Also note that it is not currently possible to request a portion of an hour.

 

design – specifies the name of the MusicMaster export design to use. By default, this is defined in the server INI and should not need to be included here. Optional

 

filename – can be used to override the path/filename in the export design. Optional

Sample Reply

<mmReply command="publishSchedule" station="ID" version="1" [userData=""] status="???????">
	<errors>
		<error>message</error>
	</errors>
</mmReply>

Reply Notes

This command does not return any schedule data. Instead, the server exports the log as it would be exported from within MusicMaster. If a non-generic interface is in use, the method used to export the schedule may vary.

Compatibility and Version Info

Available in all versions

 

This command may have a vendor specific override available and when that is the case, this command may be triggered by the Publish Schedule button in the MusicMaster Schedule Editor.